XLibre profile

Pepvoid keeps X.Org as the default X11 implementation. The optional xlibre profile allows supported Void architectures to use the community-maintained XLibre server and drivers instead:

sudo python3 cli.py x86_64 --desktop xfce --with-xlibre --mode real

The profile adds the signed XLibre Void repository, trusts its repository key, installs the xlibre, xlibre-input-drivers and xlibre-video-drivers metapackages, and removes conflicting X.Org server and driver packages from the resolved package plan. The repository configuration is retained in the installed system for future updates. It is deliberately opt-in and supports x86_64, x86_64-musl, i686, aarch64, aarch64-musl, armv7l and armv6l-musl. The builder selects the matching repository automatically for the target architecture. For x86 builds it also installs the available XLibre input and video driver packages, including Intel, AMD, Nouveau, VMware, QXL, VESA, framebuffer and legacy hardware drivers. ARM builds keep the architecture-neutral metapackages until matching driver binaries are published for those repositories.

Builder architecture	XLibre repository
x86_64, x86_64-musl, i686	XLibre Void release repository
aarch64	repository-aarch64
aarch64-musl	repository-aarch64-musl
armv7l	repository-armv7l
armv6l-musl	repository-armv6l-musl

The ARM repositories are published separately by XLibre Void under the xlibre-void/xlibre-xserver release repository. The x86 repositories continue to use the main XLibre Void release repository.

Wayland profiles are unaffected. A normal build without --with-xlibre keeps the existing X.Org packages and repositories.